blog: connecting your own AI agent to FlowFuse - #5671
Open
dimitrieh wants to merge 4 commits into
Open
Conversation
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
5 tasks
The post named ChatGPT and Claude but reached Gemini only as a CLI, and left local models out, so the approved-agent set did not match the page that leads this. It now covers the same set in the same order, with coding agents as the trailing clause, and links /ai for the per-agent path. Also missing against the page's governance section: the address itself, the requirement being MCP over HTTP, that RBAC still bounds the agent to what your own account reaches, and that actions land in the audit log marked via MCP. Adds that most agents ask before they act, and that the prompt is the agent's rather than ours. Agent, not assistant, in the policy paragraph.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
A how-to blog post for the 3.0 third-party agent feature, sitting between the
/aipage and the documentation in depth.It leads with the policy angle rather than the capability, because that is the strongest part of the story: teams under approved-AI-only rules were prompting an external tool for flow JSON and hand-importing it, so the AI was already doing the work through the clipboard. Then the mechanism, a worked example in Copilot Studio, what you grant, and the conversation with IT.
Deliberately included, because leaving them out would make it marketing rather than a guide:
No
image:in the frontmatter yet, matching the handful of 2026 posts that also omit it, so the build is fine. An Art Request is still needed before this publishes.Related Issue(s)
FlowFuse/flowfuse#8192
#5612 (blog post deliverable, sub-issue of https://github.com/FlowFuse/engineering/issues/272)
Depends on
Links to
/docs/user/expert/third-party-agents/, which lands with FlowFuse/flowfuse#8241. A link check against that path fails until it merges. Pairs with #5670 for the/aipage and the changelog.Checklist